It's not just visibility anymore. It's recommendation.

First the simplified answer:

Here’s the iron-clad reason AnswerShare is NOT cloaking. Cloaking per Google is defined as serving materially different information to search crawlers than what is on the human site, designed to manipulate search engines. AnswerShare serves Googlebot the same human site it has previously received.

These three points are offered to further clarify this assertion:

1. AnswerShare does NOT route Googlebot to the Machine AI Translation and Data Layer. Googlebot receives the human site instead. (This is not to hide anything; this is what Google wants.)
2. Google already recognizes RSS and Responsive Design — which are ALSO translations or mirrored information — and these are not deemed cloaking.
3. If a Machine Layer were an issue, then Markdown would be considered cloaking, and it is not. Cloudflare ships the same pattern as Markdown for Agents: when a client sends the Accept negotiation header with text/markdown, Cloudflare fetches the page's HTML from the origin and returns a Markdown conversion of it. Same content, machine-oriented format, chosen by the requester — which is precisely why it is not cloaking.

Additional validation details:

Cloaking, as Google defines and penalizes it, is showing search crawlers content different from what human users see, with intent to manipulate rankings. AnswerShare enforces strict bot-class separation: search-engine crawlers (Googlebot, Bingbot, Applebot, DuckDuckBot, and equivalents) always receive the identical human page, never the machine layer. Only AI-inference crawlers (GPTBot, ClaudeBot, PerplexityBot, and equivalents) receive the machine layer; Googlebot and the other search crawlers stay on the human layer. Because search crawlers and human users see the same content, the gap Google’s cloaking policy targets never exists.

Routing is by declared crawler identity — the User-Agent each AI platform publishes — and deliberately not by IP or reverse-DNS gating. That is a transparency choice: anyone, including a prospective client, can see exactly what an AI crawler receives with a single request, and nothing is hidden behind network checks. A spoofed AI user-agent gains only the same public, client-approved facts the human site already states. The content itself is structured grounding of the client’s own already-public, already-approved facts, not divergent claims built to game an algorithm. Separately, Google Search has stated it does not use llms.txt, special AI files, or Markdown to determine visibility in Search or its generative AI features — those files neither help nor hurt Google Search rankings, reinforcing that the machine layer sits outside anything Google’s ranking system evaluates. The platforms have already drawn this bot-class distinction themselves — Google-Extended is an explicit opt-in mechanism for AI use, separate from search indexing — so AnswerShare is operationalizing a line the industry has already drawn, not inventing one.